Description

• The two longest parts to build a go module is schema extraction and compilation.
• Some code changes (like a verb changing name, or sumtype changes) require compilation to happen after schema extraction so that we can generate code based on the latest schema.
• During development though, most builds will be done with compilation not dependant on schema extraction.
• This PR optimises for this case by optimistically compiling while schema extraction occurs if previous code generation is present. After the schema is extracted we then generate code and check if anything has changed that requires re-compilation.

Performance

Ran ftl dev examples/go/time, waiting for the initial builds to complete, and then modified the module code 20 times to get an average.